The McGraw-Hill 36-Hour Course : Project Management, Second Edition (McGraw-Hill 36-Hour Courses) by Helen Cooke

Author:Helen Cooke [Cooke, Helen]
Language: eng
Format: mobi
Publisher: McGraw-Hill
Published: 2010-09-27T14:00:00+00:00

Planning to Manage Change

Whatever was in the plan, reality is usually a bit different. The key concept to remember in changing things is that change gets more complex, bureaucratic, and expensive the later it occurs in the project or the life cycle of the product or deliverable. Changes made later are extremely costly.

Planning for change is cheaper than being surprised by change. A good process for capturing, prioritizing, standardizing, and distributing changes will save time and confusion as the project moves into execution. There are two levels of change to consider: change to the project plan (baseline and revisions) being used to manage the project and change to the product’s development (scope change or product configuration). Both should be placed under configuration management, and changes should be recorded against the official and most current version. The project manager and administrative team manage changes to the project; a change-resolution group will manage changes to the product. When changes to the product change the baseline plan, additional development tasks most likely will be generated as a result, with associated costs.

Adding Project Controls

Download

Copyright Disclaimer:
This site does not store any files on its server. We only index and link to content provided by other sites. Please contact the content providers to delete copyright contents if any and email us, we'll remove relevant links or contents immediately.